@jaredbusch said in Asterisk 13 CRITICAL ERROR! Required Service CHAN_SIP is disabled! This device is unusable!:

does chan_sip.so exist in /usr/lib/asterisk/modules/?

My guess is, no. But once we determined that there was no simple restoration and all evidence of chap_sip was gone from the system, they just rolled back to a snapshot from before the outage and all is well. So we might never know.

@scottalanmiller said in All Yealink Phones Down at One Site:

@dbeato said in All Yealink Phones Down at One Site:

@scottalanmiller said in All Yealink Phones Down at One Site:

@i3 said in All Yealink Phones Down at One Site:

Factory reset a phone and try manually programming? How about a packet capture at the site firewall, do you see attempts from that IP phone to where? I am assuming that the PBX is hosted elsewhere.

This is basically where we went. We did this series of events and it appears to be fixed...

Rebooted the firewall. Removed SIP-ALG, but this appears to have had no effect. Updated the firmware on each phone. Went to static DNS rather than DHCP set. DNS to CloudFlare instead of AD. Ensures STUN was on and set correctly. Added the PBX as a Proxy, manually enabled STUN for the proxy.

After those seven steps, all phones are now registered. Couldn't find any step there that individually made a difference.

To me looks like the DNS was caching something for the devices to get to. That's my theory.

If so, why did changing the DNS alone not fix it?

Not sure, I am just going by what you said. Basically very strange.

We still have the error, but we did determine that it's just an error message and the clients can register fine. The registration issue was unrelated. So not a big deal, but it would be nice to know why we get this.